Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8d46a2082842b7d3c25c9b2184ecd2ed55754b7a858ab469997029266c6e006

Tx prefix hash: 9ab504687d695eedea2c2b84a772faae23ffc547e1b6479e40ae638a4dc8c2aa
Tx public key: d0adf0e381d28ccfa8888290b0a560e5a7fea71f8b69cc896733894aaac3cd8c
Timestamp: 1750520197 Timestamp [UCT]: 2025-06-21 15:36:37 Age [y:d:h:m:s]: 00:152:08:44:39
Block: 1309849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106729 RingCT/type: yes/0
Extra: 01d0adf0e381d28ccfa8888290b0a560e5a7fea71f8b69cc896733894aaac3cd8c02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a54e19dd1db0a6b8c01a866ad1ea66a2fcba4ab3155efbf28fba95f5ed90c1f2 0.600000000000 1797466 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": 1309859, "vin": [ { "gen": { "height": 1309849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a54e19dd1db0a6b8c01a866ad1ea66a2fcba4ab3155efbf28fba95f5ed90c1f2" } } ], "extra": [ 1, 208, 173, 240, 227, 129, 210, 140, 207, 168, 136, 130, 144, 176, 165, 96, 229, 167, 254, 167, 31, 139, 105, 204, 137, 103, 51, 137, 74, 170, 195, 205, 140, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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