Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59bde75bd937b6fb3444f44d1b713c048ca5aed7f4baef3a32e234410823520a

Tx prefix hash: 69d711b23789f4fea7ba83dd5b655da1308a5570b98cec67049a9b41b9b904cf
Tx public key: 7f153ecd863f17f14aa743b0f3dd8c495bbd1ec83e2bb6eaa6beef3ae896d8a0
Timestamp: 1731706455 Timestamp [UCT]: 2024-11-15 21:34:15 Age [y:d:h:m:s]: 00:135:05:00:16
Block: 1154507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96456 RingCT/type: yes/0
Extra: 017f153ecd863f17f14aa743b0f3dd8c495bbd1ec83e2bb6eaa6beef3ae896d8a0021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a17abf9bdfe6670a7d7ebd6cb89e5d519d0f12b82c1e33be744050086697c9a 0.600000000000 1640120 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": 1154517, "vin": [ { "gen": { "height": 1154507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a17abf9bdfe6670a7d7ebd6cb89e5d519d0f12b82c1e33be744050086697c9a" } } ], "extra": [ 1, 127, 21, 62, 205, 134, 63, 23, 241, 74, 167, 67, 176, 243, 221, 140, 73, 91, 189, 30, 200, 62, 43, 182, 234, 166, 190, 239, 58, 232, 150, 216, 160, 2, 17, 0, 0, 0, 4, 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