Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 025dde362e3782de7dcbb194e55e97578baa96c429105d783d9bce6619f31816

Tx prefix hash: c38320cd1f255ede7a8688ca7024533b14de6e1d0c4e6f7a2bb91b749d8f5ca9
Tx public key: b6de5952f8126bc3d8313bd2b47af43d026e1043d2702179a04e6cd2a6c6b0e0
Timestamp: 1737028113 Timestamp [UCT]: 2025-01-16 11:48:33 Age [y:d:h:m:s]: 00:152:08:10:48
Block: 1198577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108592 RingCT/type: yes/0
Extra: 01b6de5952f8126bc3d8313bd2b47af43d026e1043d2702179a04e6cd2a6c6b0e0021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 148008b8c7f861d6baaca8a1f6132c69809237e70b87f260eb2dad2ce81348e9 0.600000000000 1685202 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": 1198587, "vin": [ { "gen": { "height": 1198577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "148008b8c7f861d6baaca8a1f6132c69809237e70b87f260eb2dad2ce81348e9" } } ], "extra": [ 1, 182, 222, 89, 82, 248, 18, 107, 195, 216, 49, 59, 210, 180, 122, 244, 61, 2, 110, 16, 67, 210, 112, 33, 121, 160, 78, 108, 210, 166, 198, 176, 224, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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