Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcd0db6476063ce61d54066bc60fbf3187d9e8387e42ab8314a10fb330ec1cf8

Tx prefix hash: 13487cd108e28c7d95287954f0bed18fa05925519e4f14b4df5dee5d7c35d808
Tx public key: 00fb1d75042d11ecbc4f9cce12d62cb90bfbdb761b0fdc446d5c62889f7939bf
Timestamp: 1745051503 Timestamp [UCT]: 2025-04-19 08:31:43 Age [y:d:h:m:s]: 00:022:22:51:21
Block: 1264740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16415 RingCT/type: yes/0
Extra: 0100fb1d75042d11ecbc4f9cce12d62cb90bfbdb761b0fdc446d5c62889f7939bf0211000000046c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 716f519c6313b9670e4fe6451818fdd1781d77e4aa5ba9c3d1a2cdd63fb6db97 0.600000000000 1751941 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": 1264750, "vin": [ { "gen": { "height": 1264740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "716f519c6313b9670e4fe6451818fdd1781d77e4aa5ba9c3d1a2cdd63fb6db97" } } ], "extra": [ 1, 0, 251, 29, 117, 4, 45, 17, 236, 188, 79, 156, 206, 18, 214, 44, 185, 11, 251, 219, 118, 27, 15, 220, 68, 109, 92, 98, 136, 159, 121, 57, 191, 2, 17, 0, 0, 0, 4, 108, 152, 170, 61, 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