Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 504d54ab8eb5558f369f3fa106f371a3d1141dd29cbdb5f91a5348eeb18a007f

Tx prefix hash: 7d53f70b44f4470dd4c8238f9cdb499150348532b9a5b05164bcaa8c755bad8c
Tx public key: 0a94eee8d0a0c0e2ffa1274cf0f249c56fd947aab9083e8537eaf0b4ace97efe
Timestamp: 1736623069 Timestamp [UCT]: 2025-01-11 19:17:49 Age [y:d:h:m:s]: 00:162:04:04:57
Block: 1195223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115523 RingCT/type: yes/0
Extra: 010a94eee8d0a0c0e2ffa1274cf0f249c56fd947aab9083e8537eaf0b4ace97efe0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 517ab7d13112496c6b832cbd61f7489620f4a51b985afb53642c31601767d359 0.600000000000 1681812 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": 1195233, "vin": [ { "gen": { "height": 1195223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "517ab7d13112496c6b832cbd61f7489620f4a51b985afb53642c31601767d359" } } ], "extra": [ 1, 10, 148, 238, 232, 208, 160, 192, 226, 255, 161, 39, 76, 240, 242, 73, 197, 111, 217, 71, 170, 185, 8, 62, 133, 55, 234, 240, 180, 172, 233, 126, 254, 2, 17, 0, 0, 0, 6, 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