Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7296280d51d1f05d178c6cef2a6635cd93318c157251d600e4d58e40272b734d

Tx prefix hash: 72648573cf76dae0c7876b633ebfb39bb2d9a2fb04a2e7f016f683489f09cec7
Tx public key: 02e41d93ff2057f0f6ba354fda0de7f957f0bd6c1ed25b452e4ac9d29ca120f1
Timestamp: 1756684497 Timestamp [UCT]: 2025-08-31 23:54:57 Age [y:d:h:m:s]: 00:070:21:43:42
Block: 1358707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50644 RingCT/type: yes/0
Extra: 0102e41d93ff2057f0f6ba354fda0de7f957f0bd6c1ed25b452e4ac9d29ca120f1021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c93106c5a293bc3a8a457dd2eeeea54866b98b2252eb9214f01f1e85420d55a 0.600000000000 1846720 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": 1358717, "vin": [ { "gen": { "height": 1358707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c93106c5a293bc3a8a457dd2eeeea54866b98b2252eb9214f01f1e85420d55a" } } ], "extra": [ 1, 2, 228, 29, 147, 255, 32, 87, 240, 246, 186, 53, 79, 218, 13, 231, 249, 87, 240, 189, 108, 30, 210, 91, 69, 46, 74, 201, 210, 156, 161, 32, 241, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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