Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48b82e54993d94866118aa4e3b61faf764bf2a96d5ac6a97b5d3699acc119326

Tx prefix hash: 1aa4996e2cde898b1d573037ee50b3f8e7fba8289f8d916595ef9d0a472e99b6
Tx public key: 4e26492b7cc3f6e12bfae67a32580d65e99b7421758760d869a12418a94c2d8e
Timestamp: 1736232074 Timestamp [UCT]: 2025-01-07 06:41:14 Age [y:d:h:m:s]: 00:160:07:50:24
Block: 1191994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114308 RingCT/type: yes/0
Extra: 014e26492b7cc3f6e12bfae67a32580d65e99b7421758760d869a12418a94c2d8e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4331e99a36031f37e562fc94d6189783f534b44f0a1657e1da4c609b41a63b7 0.600000000000 1678539 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": 1192004, "vin": [ { "gen": { "height": 1191994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4331e99a36031f37e562fc94d6189783f534b44f0a1657e1da4c609b41a63b7" } } ], "extra": [ 1, 78, 38, 73, 43, 124, 195, 246, 225, 43, 250, 230, 122, 50, 88, 13, 101, 233, 155, 116, 33, 117, 135, 96, 216, 105, 161, 36, 24, 169, 76, 45, 142, 2, 17, 0, 0, 0, 2, 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