Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a449f50b3aa7dd51e46813ba9a5db5b9036e55898a46f8507d5d3cae3600979

Tx prefix hash: 7a4d58e374c46ec83679c6b85bdbbaf55787d17fa583ae259bbe9ae3671ecbdb
Tx public key: a0659a537af12612e12ccd8cda7e65b8f49aec48572c22c53268c6657bf85bfc
Timestamp: 1578931589 Timestamp [UCT]: 2020-01-13 16:06:29 Age [y:d:h:m:s]: 05:002:15:47:11
Block: 44786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152242 RingCT/type: yes/0
Extra: 01a0659a537af12612e12ccd8cda7e65b8f49aec48572c22c53268c6657bf85bfc0211000000094ac5aa02000000000000000000

1 output(s) for total of 436.120228612000 dcy

stealth address amount amount idx
00: 55b3fa4c7962f3886b8821054c86b12d90d1cb6f4840d50487f1c4e1e6f117b4 436.120228612000 81600 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": 44796, "vin": [ { "gen": { "height": 44786 } } ], "vout": [ { "amount": 436120228612, "target": { "key": "55b3fa4c7962f3886b8821054c86b12d90d1cb6f4840d50487f1c4e1e6f117b4" } } ], "extra": [ 1, 160, 101, 154, 83, 122, 241, 38, 18, 225, 44, 205, 140, 218, 126, 101, 184, 244, 154, 236, 72, 87, 44, 34, 197, 50, 104, 198, 101, 123, 248, 91, 252, 2, 17, 0, 0, 0, 9, 74, 197, 170, 2, 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