Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48d6c5781a8dea6d8c67eb4d8a25c480f689fcc2267fe3811f44ce871adfa5d1

Tx prefix hash: 6602b0a3eec780c19464bfc17f577c8feeecb9694969dba98b381d9d2c624ebc
Tx public key: 3b1d99f73071c888cda9ae9020b0a801a3f87ab02401732d9ef606fa4ea69b63
Timestamp: 1745500114 Timestamp [UCT]: 2025-04-24 13:08:34 Age [y:d:h:m:s]: 00:210:12:23:48
Block: 1268453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148163 RingCT/type: yes/0
Extra: 013b1d99f73071c888cda9ae9020b0a801a3f87ab02401732d9ef606fa4ea69b630211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2547fcb92dae0a33a226eb33183c404079550f640638747f0dc13bf8a4e5379 0.600000000000 1755682 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": 1268463, "vin": [ { "gen": { "height": 1268453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2547fcb92dae0a33a226eb33183c404079550f640638747f0dc13bf8a4e5379" } } ], "extra": [ 1, 59, 29, 153, 247, 48, 113, 200, 136, 205, 169, 174, 144, 32, 176, 168, 1, 163, 248, 122, 176, 36, 1, 115, 45, 158, 246, 6, 250, 78, 166, 155, 99, 2, 17, 0, 0, 0, 6, 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