Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 498182519f277f68d8233710d3f9efcbc366bfdcd2d8b7a5b91e91961d2aa006

Tx prefix hash: f3fe93a917e362cbe000b17181fa7bc5d5a240f1a163278265e596ad6b7170ab
Tx public key: 0a1f1870b4a010a501a363863bf4ab2549000a0dc18ee1e363f0ed7612c56f6d
Timestamp: 1754352296 Timestamp [UCT]: 2025-08-05 00:04:56 Age [y:d:h:m:s]: 00:015:19:17:10
Block: 1340424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10356 RingCT/type: yes/0
Extra: 010a1f1870b4a010a501a363863bf4ab2549000a0dc18ee1e363f0ed7612c56f6d0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f0574b0959d2b7dbb08b8635bff95dc1f7d895f7534a9cd8c74d0c24d0153bd 0.600000000000 1828241 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": 1340434, "vin": [ { "gen": { "height": 1340424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f0574b0959d2b7dbb08b8635bff95dc1f7d895f7534a9cd8c74d0c24d0153bd" } } ], "extra": [ 1, 10, 31, 24, 112, 180, 160, 16, 165, 1, 163, 99, 134, 59, 244, 171, 37, 73, 0, 10, 13, 193, 142, 225, 227, 99, 240, 237, 118, 18, 197, 111, 109, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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