Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac5eef12dc989c39e211e8f9480e15f55716c2e14ea32a08919f615588f221b7

Tx prefix hash: 67715c644d2eaf9167dd73a7b947904d81297ec64d31e1aeb97611097d2fba71
Tx public key: 9aff908df5d0d4629f208bfb55f69948b3b301626eff25b70f42bb09e558ee0a
Timestamp: 1728036148 Timestamp [UCT]: 2024-10-04 10:02:28 Age [y:d:h:m:s]: 00:218:10:07:07
Block: 1124187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155912 RingCT/type: yes/0
Extra: 019aff908df5d0d4629f208bfb55f69948b3b301626eff25b70f42bb09e558ee0a02110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ef95ab663295d2050090b0cef7c4d69bc9b5482a2a5bade239e55de065fbb1f 0.600000000000 1606772 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": 1124197, "vin": [ { "gen": { "height": 1124187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ef95ab663295d2050090b0cef7c4d69bc9b5482a2a5bade239e55de065fbb1f" } } ], "extra": [ 1, 154, 255, 144, 141, 245, 208, 212, 98, 159, 32, 139, 251, 85, 246, 153, 72, 179, 179, 1, 98, 110, 255, 37, 183, 15, 66, 187, 9, 229, 88, 238, 10, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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