Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1f65e98f0456639d17c55a0d60ca7a08170b651579f8138323cb1250e4f8821

Tx prefix hash: 39b58d79aced196e54b62f917203feda6392c372cf4a71cd11daf8a6870757c7
Tx public key: b17bab6eab3c336badc531606f71967fd2dd51bb64bdf5af5c8d4b34f6a00bd5
Timestamp: 1578820080 Timestamp [UCT]: 2020-01-12 09:08:00 Age [y:d:h:m:s]: 04:356:06:29:20
Block: 43807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144158 RingCT/type: yes/0
Extra: 01b17bab6eab3c336badc531606f71967fd2dd51bb64bdf5af5c8d4b34f6a00bd50211000000084ac5aa02000000000000000000

1 output(s) for total of 439.397476034000 dcy

stealth address amount amount idx
00: a734f18754c5740615cf205fd38c92f46068525e647b66f790327df6c8b16e8a 439.397476034000 79473 of 0

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": 43817, "vin": [ { "gen": { "height": 43807 } } ], "vout": [ { "amount": 439397476034, "target": { "key": "a734f18754c5740615cf205fd38c92f46068525e647b66f790327df6c8b16e8a" } } ], "extra": [ 1, 177, 123, 171, 110, 171, 60, 51, 107, 173, 197, 49, 96, 111, 113, 150, 127, 210, 221, 81, 187, 100, 189, 245, 175, 92, 141, 75, 52, 246, 160, 11, 213, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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