Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cd8e6abf332d043eac06b5f6b5211b442ac8e8f5f013991ea9b1aed7c33e7f5

Tx prefix hash: 4fe300aafe4c39863954394abd5057f6b92fac1c35b79890a3712aae3908367b
Tx public key: e83129e0618341048814fd8aa41575d00b6cf6aaa457d2a4090590ab9e241e49
Timestamp: 1735560584 Timestamp [UCT]: 2024-12-30 12:09:44 Age [y:d:h:m:s]: 00:305:08:05:16
Block: 1186429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215737 RingCT/type: yes/0
Extra: 01e83129e0618341048814fd8aa41575d00b6cf6aaa457d2a4090590ab9e241e49021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eed10d3e046b3ce938d48eefa4239cd7ec24dc840cfae563121d4d27978a696d 0.600000000000 1672910 of 15

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": 1186439, "vin": [ { "gen": { "height": 1186429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eed10d3e046b3ce938d48eefa4239cd7ec24dc840cfae563121d4d27978a696d" } } ], "extra": [ 1, 232, 49, 41, 224, 97, 131, 65, 4, 136, 20, 253, 138, 164, 21, 117, 208, 11, 108, 246, 170, 164, 87, 210, 164, 9, 5, 144, 171, 158, 36, 30, 73, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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