Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3490c34330ec18ce316400df6f09fc404ed8c1ab358b61c75e221c576f08a5

Tx prefix hash: bd5db8df43aba897cc42dc4c9e9d34a46811d1a1708f3aeb2494956765fda355
Tx public key: c9445a3b2b269bc4b83f7dc0c299e1243b93dfa2af4f791c0db450281b7e26cb
Timestamp: 1751108478 Timestamp [UCT]: 2025-06-28 11:01:18 Age [y:d:h:m:s]: 00:140:15:26:52
Block: 1314474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98605 RingCT/type: yes/0
Extra: 01c9445a3b2b269bc4b83f7dc0c299e1243b93dfa2af4f791c0db450281b7e26cb021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c74ca9d3594b50ba1175c16989adcb951ef6854fd4dc950a61b10c18be58e701 0.600000000000 1802121 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": 1314484, "vin": [ { "gen": { "height": 1314474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c74ca9d3594b50ba1175c16989adcb951ef6854fd4dc950a61b10c18be58e701" } } ], "extra": [ 1, 201, 68, 90, 59, 43, 38, 155, 196, 184, 63, 125, 192, 194, 153, 225, 36, 59, 147, 223, 162, 175, 79, 121, 28, 13, 180, 80, 40, 27, 126, 38, 203, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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