Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340227c6d69babdb66df6bec178027d985e3d740da9003c15bd734091e53eee9

Tx prefix hash: 7151e2339a71776790020ed06f02239b121de0ffa21eac28abf221b589755d9d
Tx public key: bd7e6acc36b91c5ea010afddb5c521eae7aa84c746c307af6eeb371962ba42fd
Timestamp: 1735860104 Timestamp [UCT]: 2025-01-02 23:21:44 Age [y:d:h:m:s]: 00:165:23:37:10
Block: 1188908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118338 RingCT/type: yes/0
Extra: 01bd7e6acc36b91c5ea010afddb5c521eae7aa84c746c307af6eeb371962ba42fd021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aef5ad0d4efb77a963bbb1a4640a23abd088e568064baf2f07340a260a4e6d7c 0.600000000000 1675413 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": 1188918, "vin": [ { "gen": { "height": 1188908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aef5ad0d4efb77a963bbb1a4640a23abd088e568064baf2f07340a260a4e6d7c" } } ], "extra": [ 1, 189, 126, 106, 204, 54, 185, 28, 94, 160, 16, 175, 221, 181, 197, 33, 234, 231, 170, 132, 199, 70, 195, 7, 175, 110, 235, 55, 25, 98, 186, 66, 253, 2, 17, 0, 0, 0, 2, 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