Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b4d439e64a3096da6d200924f3f626e7bf172128aef60aac8171d373d4fa00b

Tx prefix hash: 916810483594ecf3c7e8b7c8e1730e6330e307e28f40255d0ae5f64042b28192
Tx public key: 035864fbe7a7a0cc9e604b3e2429dc4c0e365e0be0ba3f29dc2e75f043894add
Timestamp: 1723301974 Timestamp [UCT]: 2024-08-10 14:59:34 Age [y:d:h:m:s]: 00:233:21:40:43
Block: 1084933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167043 RingCT/type: yes/0
Extra: 01035864fbe7a7a0cc9e604b3e2429dc4c0e365e0be0ba3f29dc2e75f043894add02110000000e91e13c04000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: d543c226a861f2c733c20c3944703a6262c6246c4fd498181f4a66213210dc13 0.615610000000 1559384 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": 1084943, "vin": [ { "gen": { "height": 1084933 } } ], "vout": [ { "amount": 615610000, "target": { "key": "d543c226a861f2c733c20c3944703a6262c6246c4fd498181f4a66213210dc13" } } ], "extra": [ 1, 3, 88, 100, 251, 231, 167, 160, 204, 158, 96, 75, 62, 36, 41, 220, 76, 14, 54, 94, 11, 224, 186, 63, 41, 220, 46, 117, 240, 67, 137, 74, 221, 2, 17, 0, 0, 0, 14, 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