Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5529212509c7f8d9191490b75f32922b0dc593b416f6b05766757dd7556daa9e

Tx prefix hash: 4a319d7d680f2fd0ca4e27c13702ee1eb208e1a921209116e10a890fac203ab3
Tx public key: 86e5b2af18a73bf0e433e3440efdb8bd6c138f9e6e0691514530d1ba7d606e3a
Timestamp: 1733118837 Timestamp [UCT]: 2024-12-02 05:53:57 Age [y:d:h:m:s]: 00:112:16:03:36
Block: 1166224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80306 RingCT/type: yes/0
Extra: 0186e5b2af18a73bf0e433e3440efdb8bd6c138f9e6e0691514530d1ba7d606e3a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bac8a4fc471e0ff92d6afbbd0b6a7929753ae5ccaaac6e5663300f13658d8352 0.600000000000 1651901 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": 1166234, "vin": [ { "gen": { "height": 1166224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bac8a4fc471e0ff92d6afbbd0b6a7929753ae5ccaaac6e5663300f13658d8352" } } ], "extra": [ 1, 134, 229, 178, 175, 24, 167, 59, 240, 228, 51, 227, 68, 14, 253, 184, 189, 108, 19, 143, 158, 110, 6, 145, 81, 69, 48, 209, 186, 125, 96, 110, 58, 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