Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb535849efc79ea8c4a4cf8bb1c741b05de864d2ca8c9858b260e8d6d797b723

Tx prefix hash: 9b08721485e98f71259a3d2010ce4a9ef77e962a11e6f1d6a3c6fccbf72883dd
Tx public key: de32c9d2b0c931b6ac5afe602bb28991e9e6550cbf98111c0977de3def2a3d9f
Timestamp: 1744214726 Timestamp [UCT]: 2025-04-09 16:05:26 Age [y:d:h:m:s]: 00:294:17:51:09
Block: 1257802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208311 RingCT/type: yes/0
Extra: 01de32c9d2b0c931b6ac5afe602bb28991e9e6550cbf98111c0977de3def2a3d9f0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70cb41d3a50fedf2a0f6967f6639150f1c510418f60360e14f95e0784a3f7253 0.600000000000 1744933 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": 1257812, "vin": [ { "gen": { "height": 1257802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70cb41d3a50fedf2a0f6967f6639150f1c510418f60360e14f95e0784a3f7253" } } ], "extra": [ 1, 222, 50, 201, 210, 176, 201, 49, 182, 172, 90, 254, 96, 43, 178, 137, 145, 233, 230, 85, 12, 191, 152, 17, 28, 9, 119, 222, 61, 239, 42, 61, 159, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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