Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abbcb24f63b5d09c6c2f74b6edaee14c575fab810c626a0df9ff10a7f78918b9

Tx prefix hash: c752080d8a95556efa06b4f9440edf8ba00b1723f1a6db2ee0cc75e1bcf482d8
Tx public key: 93b32f320a54ebfa7aae2bf61e2e74ea0c02c6d97a7399e6628a0cfb89203f89
Timestamp: 1583753133 Timestamp [UCT]: 2020-03-09 11:25:33 Age [y:d:h:m:s]: 04:303:20:49:02
Block: 79415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111919 RingCT/type: yes/0
Extra: 0193b32f320a54ebfa7aae2bf61e2e74ea0c02c6d97a7399e6628a0cfb89203f8902110000000178e4872e000000000000000000

1 output(s) for total of 334.862048028000 dcy

stealth address amount amount idx
00: a1c09785481cb7541019c02e0027d184cedf136a712222eed892721e64a3334f 334.862048028000 145247 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": 79425, "vin": [ { "gen": { "height": 79415 } } ], "vout": [ { "amount": 334862048028, "target": { "key": "a1c09785481cb7541019c02e0027d184cedf136a712222eed892721e64a3334f" } } ], "extra": [ 1, 147, 179, 47, 50, 10, 84, 235, 250, 122, 174, 43, 246, 30, 46, 116, 234, 12, 2, 198, 217, 122, 115, 153, 230, 98, 138, 12, 251, 137, 32, 63, 137, 2, 17, 0, 0, 0, 1, 120, 228, 135, 46, 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