Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b029e1d9f2d01cd30cd2cd877e967d6717fc7be365caa1b41512743528eaadd1

Tx prefix hash: f30e3b68020161743150034956a9b0b1d4be5b25600687e4779fb47b971451a9
Tx public key: b7cf1d190e3775b6e0a5a21f1c1130e8c6662a646d4dfc6ee2236e27876fd798
Timestamp: 1578832994 Timestamp [UCT]: 2020-01-12 12:43:14 Age [y:d:h:m:s]: 04:311:05:31:33
Block: 43959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111890 RingCT/type: yes/0
Extra: 01b7cf1d190e3775b6e0a5a21f1c1130e8c6662a646d4dfc6ee2236e27876fd7980211000000cf17786bcf000000000000000000

1 output(s) for total of 438.880643043000 dcy

stealth address amount amount idx
00: d39f2d23df8411a958b56b46a5ae883c806fd915914f3a54f6737935f5e9311f 438.880643043000 79812 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": 43969, "vin": [ { "gen": { "height": 43959 } } ], "vout": [ { "amount": 438880643043, "target": { "key": "d39f2d23df8411a958b56b46a5ae883c806fd915914f3a54f6737935f5e9311f" } } ], "extra": [ 1, 183, 207, 29, 25, 14, 55, 117, 182, 224, 165, 162, 31, 28, 17, 48, 232, 198, 102, 42, 100, 109, 77, 252, 110, 226, 35, 110, 39, 135, 111, 215, 152, 2, 17, 0, 0, 0, 207, 23, 120, 107, 207, 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