Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84bdd31e518620a40d235d1becee7889907746d67f249199049a0b7fa31f791

Tx prefix hash: 618e5f08ae519d485d3abe48c517d02affe29f3b7a31d9ec9759eb994c9638d4
Tx public key: 7c3cba372872ef20da0a61032eabd81401dc77a545853341e6e4b596f26f5ab9
Timestamp: 1581824681 Timestamp [UCT]: 2020-02-16 03:44:41 Age [y:d:h:m:s]: 05:259:08:22:48
Block: 66062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1335858 RingCT/type: yes/0
Extra: 017c3cba372872ef20da0a61032eabd81401dc77a545853341e6e4b596f26f5ab90211000000017adf42d3000000000000000000

1 output(s) for total of 370.801434065000 dcy

stealth address amount amount idx
00: 61ed520249c8c9f3d01c268b4f3f1daca5a8214821fde8160f7a6868f98f5065 370.801434065000 121709 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": 66072, "vin": [ { "gen": { "height": 66062 } } ], "vout": [ { "amount": 370801434065, "target": { "key": "61ed520249c8c9f3d01c268b4f3f1daca5a8214821fde8160f7a6868f98f5065" } } ], "extra": [ 1, 124, 60, 186, 55, 40, 114, 239, 32, 218, 10, 97, 3, 46, 171, 216, 20, 1, 220, 119, 165, 69, 133, 51, 65, 230, 228, 181, 150, 242, 111, 90, 185, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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