Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3efc9262ff11d331db6d16e1a3ded48fcf0009b14f3788c9e45ba7c1fafcef9b

Tx prefix hash: e7811fecfb44c823f60c7aba29cdad76099afd6ff6b9d5532de5f69895c6f311
Tx public key: c1b9cef18bae3fb4242900b75442b565f8b5a0cadfcf9eea917c2a013a8e7fa1
Timestamp: 1648009708 Timestamp [UCT]: 2022-03-23 04:28:28 Age [y:d:h:m:s]: 02:356:18:07:20
Block: 464431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774276 RingCT/type: yes/0
Extra: 01c1b9cef18bae3fb4242900b75442b565f8b5a0cadfcf9eea917c2a013a8e7fa1021100000001d3fcec30000000000000000000

1 output(s) for total of 17.747923993000 dcy

stealth address amount amount idx
00: 99a982c506db4d2d6e0603301c04b086d4faac85c41733656afda7ec6ff23934 17.747923993000 882314 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 464441, "vin": [ { "gen": { "height": 464431 } } ], "vout": [ { "amount": 17747923993, "target": { "key": "99a982c506db4d2d6e0603301c04b086d4faac85c41733656afda7ec6ff23934" } } ], "extra": [ 1, 193, 185, 206, 241, 139, 174, 63, 180, 36, 41, 0, 183, 84, 66, 181, 101, 248, 181, 160, 202, 223, 207, 158, 234, 145, 124, 42, 1, 58, 142, 127, 161, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8