Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bd507ea81ae59b4cace3f0ee3dc1ea6b23acc67aa0ab9bd374160cc06f74397

Tx prefix hash: 64325226b4dcfcac8c7384eb36c609edce1435ae8830974cb48d0148fd814732
Tx public key: 6dfadb73ec0198f0fba28c8bf01aeb5da01866bb6f4f87ff7c41f9b7d18b90af
Timestamp: 1735759403 Timestamp [UCT]: 2025-01-01 19:23:23 Age [y:d:h:m:s]: 00:170:08:10:19
Block: 1188073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121409 RingCT/type: yes/0
Extra: 016dfadb73ec0198f0fba28c8bf01aeb5da01866bb6f4f87ff7c41f9b7d18b90af0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd8219e6ea2f799cf647c1cc3cdad377c44f2328c03c51d07b2ba41c7372da44 0.600000000000 1674572 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": 1188083, "vin": [ { "gen": { "height": 1188073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd8219e6ea2f799cf647c1cc3cdad377c44f2328c03c51d07b2ba41c7372da44" } } ], "extra": [ 1, 109, 250, 219, 115, 236, 1, 152, 240, 251, 162, 140, 139, 240, 26, 235, 93, 160, 24, 102, 187, 111, 79, 135, 255, 124, 65, 249, 183, 209, 139, 144, 175, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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