Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aef0c0b12a5861bee523da358ea11c6aebb57ad5971a65c15396fa3041372067

Tx prefix hash: 191815a28de6ad5ab495f02ef070022b61c227fb5ae356b26c2eed3bc0d50393
Tx public key: 44606917f35b1bd81b0d6ad6a51b2ad771f1f9f313de56fd18f82ddc33088ff1
Timestamp: 1582729061 Timestamp [UCT]: 2020-02-26 14:57:41 Age [y:d:h:m:s]: 04:341:18:45:58
Block: 72430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137272 RingCT/type: yes/0
Extra: 0144606917f35b1bd81b0d6ad6a51b2ad771f1f9f313de56fd18f82ddc33088ff10211000000104943cd9f000000000000000000

1 output(s) for total of 353.197518521000 dcy

stealth address amount amount idx
00: e7546ea714d3aa3d236714c78aff7c4bed9c911bf4bc66ed7361dc59def46a7c 353.197518521000 133790 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": 72440, "vin": [ { "gen": { "height": 72430 } } ], "vout": [ { "amount": 353197518521, "target": { "key": "e7546ea714d3aa3d236714c78aff7c4bed9c911bf4bc66ed7361dc59def46a7c" } } ], "extra": [ 1, 68, 96, 105, 23, 243, 91, 27, 216, 27, 13, 106, 214, 165, 27, 42, 215, 113, 241, 249, 243, 19, 222, 86, 253, 24, 248, 45, 220, 51, 8, 143, 241, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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