Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba7a298d429381d4edb3dab9b3de04ab3b85034e58dcc9bcd423029efa91e9b

Tx prefix hash: 5265e656b3c4dc244c5edd395d032beba63f510ad7795bb1e538d5d10a73a64b
Tx public key: fe2d89fcc2a5b9f2fadce4f4b5b1c728419f2d620433ac88b8579b0506183377
Timestamp: 1728096531 Timestamp [UCT]: 2024-10-05 02:48:51 Age [y:d:h:m:s]: 01:057:07:48:56
Block: 1124673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299387 RingCT/type: yes/0
Extra: 01fe2d89fcc2a5b9f2fadce4f4b5b1c728419f2d620433ac88b8579b0506183377021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d100e7234e1f4b686773077842bfd89fac30cfed15f0b8c2ad2e5009a34005d5 0.600000000000 1607334 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": 1124683, "vin": [ { "gen": { "height": 1124673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d100e7234e1f4b686773077842bfd89fac30cfed15f0b8c2ad2e5009a34005d5" } } ], "extra": [ 1, 254, 45, 137, 252, 194, 165, 185, 242, 250, 220, 228, 244, 181, 177, 199, 40, 65, 159, 45, 98, 4, 51, 172, 136, 184, 87, 155, 5, 6, 24, 51, 119, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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