Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 902a04b03d571a456a6f801bc3d415edaef7643dd52414f2176dc6dfe4ca66e7

Tx prefix hash: c943a93a88aa5b02d49a0e05a276dc17ad27c9ed846270920b923468e4d96a18
Tx public key: 482e3a31ba813259243894b813fd4718152022198962b2767d8fa286d13673c1
Timestamp: 1581952087 Timestamp [UCT]: 2020-02-17 15:08:07 Age [y:d:h:m:s]: 04:272:12:33:24
Block: 66967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1087010 RingCT/type: yes/0
Extra: 01482e3a31ba813259243894b813fd4718152022198962b2767d8fa286d13673c10211000000038a2ee0d9000000000000000000

1 output(s) for total of 368.251391036000 dcy

stealth address amount amount idx
00: 1d43f556f8809bb14aeadbc7bc5e7b43e5d3fb392efa602bf2697e2b9591a652 368.251391036000 123254 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": 66977, "vin": [ { "gen": { "height": 66967 } } ], "vout": [ { "amount": 368251391036, "target": { "key": "1d43f556f8809bb14aeadbc7bc5e7b43e5d3fb392efa602bf2697e2b9591a652" } } ], "extra": [ 1, 72, 46, 58, 49, 186, 129, 50, 89, 36, 56, 148, 184, 19, 253, 71, 24, 21, 32, 34, 25, 137, 98, 178, 118, 125, 143, 162, 134, 209, 54, 115, 193, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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