Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2473f97b1b04f20679ce08735f5621f3967254287c62c1de6a68353cab78fba7

Tx prefix hash: b3eae1230c968735b6f47ce5b0e1aefa3cc723cb01be6c0c8465502b348f77e0
Tx public key: 12194cc8eddd52ca5a95a34ed4bac166e5cbf8a5212f24b832e62dfd9d45eb8a
Timestamp: 1577965939 Timestamp [UCT]: 2020-01-02 11:52:19 Age [y:d:h:m:s]: 05:007:03:02:42
Block: 37196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155047 RingCT/type: yes/0
Extra: 0112194cc8eddd52ca5a95a34ed4bac166e5cbf8a5212f24b832e62dfd9d45eb8a021100000016dafe52e4000000000000000000

1 output(s) for total of 462.120317388000 dcy

stealth address amount amount idx
00: 7b12866a998048d1210dfd4bbe18dedb8b8f94dbb22026ead442402bf81413dd 462.120317388000 63064 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": 37206, "vin": [ { "gen": { "height": 37196 } } ], "vout": [ { "amount": 462120317388, "target": { "key": "7b12866a998048d1210dfd4bbe18dedb8b8f94dbb22026ead442402bf81413dd" } } ], "extra": [ 1, 18, 25, 76, 200, 237, 221, 82, 202, 90, 149, 163, 78, 212, 186, 193, 102, 229, 203, 248, 165, 33, 47, 36, 184, 50, 230, 45, 253, 157, 69, 235, 138, 2, 17, 0, 0, 0, 22, 218, 254, 82, 228, 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