Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c06d17717dddfd07c0b6b83ddd80b0e245f3f6be00c0d498d4b62210d770a40d

Tx prefix hash: 39d57c051334c2b6d31c44dde37fae240e4ee3a30ceb47564727b4f27ef7563a
Tx public key: 8afab638db8775ed4f5a06c56b28f2376ea34163cd3a655d272ad357fce05327
Timestamp: 1577929150 Timestamp [UCT]: 2020-01-02 01:39:10 Age [y:d:h:m:s]: 04:309:13:51:23
Block: 36802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110373 RingCT/type: yes/0
Extra: 018afab638db8775ed4f5a06c56b28f2376ea34163cd3a655d272ad357fce05327021100000007d81c26c0000000000000000000

1 output(s) for total of 463.511537739000 dcy

stealth address amount amount idx
00: 6df8479f3eb60d87cbe048c67c41d37d7c2f1667fe7ee68a86939c22b2169d13 463.511537739000 62384 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": 36812, "vin": [ { "gen": { "height": 36802 } } ], "vout": [ { "amount": 463511537739, "target": { "key": "6df8479f3eb60d87cbe048c67c41d37d7c2f1667fe7ee68a86939c22b2169d13" } } ], "extra": [ 1, 138, 250, 182, 56, 219, 135, 117, 237, 79, 90, 6, 197, 107, 40, 242, 55, 110, 163, 65, 99, 205, 58, 101, 93, 39, 42, 211, 87, 252, 224, 83, 39, 2, 17, 0, 0, 0, 7, 216, 28, 38, 192, 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