Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ed289ad248b0365d918d24d1617064538182bf04033ddfb03d4788f2383b5b3

Tx prefix hash: f1eafc59486a1a3e57a0e845b533b1d794a8fe98f6105e6f9bf03edea78dd606
Tx public key: 4b07edd3d3caaac6b93be416b1e1aeb7d8f392aa6deb37f85ea935f49f055fe0
Timestamp: 1763362123 Timestamp [UCT]: 2025-11-17 06:48:43 Age [y:d:h:m:s]: 00:004:07:20:48
Block: 1413921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3074 RingCT/type: yes/0
Extra: 014b07edd3d3caaac6b93be416b1e1aeb7d8f392aa6deb37f85ea935f49f055fe0021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c255a0454bf98413122112e4e013eb3362802af7dfc4401fc2138ac83a1c1eff 0.600000000000 1902402 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": 1413931, "vin": [ { "gen": { "height": 1413921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c255a0454bf98413122112e4e013eb3362802af7dfc4401fc2138ac83a1c1eff" } } ], "extra": [ 1, 75, 7, 237, 211, 211, 202, 170, 198, 185, 59, 228, 22, 177, 225, 174, 183, 216, 243, 146, 170, 109, 235, 55, 248, 94, 169, 53, 244, 159, 5, 95, 224, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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