Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e60420c68162306881a31deb8a269ce3da42cb1c0f7f31d1b4e7d871b08e0e

Tx prefix hash: da061963d59c4f37e3975dd9480f94454f3156dfe404f22bb0f7692f17f74587
Tx public key: ca82c3bfe64623018364bc3ee7c4bd7f25c28203737e1dd75668afd03857a64f
Timestamp: 1578236897 Timestamp [UCT]: 2020-01-05 15:08:17 Age [y:d:h:m:s]: 05:024:14:46:39
Block: 39273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1167470 RingCT/type: yes/0
Extra: 01ca82c3bfe64623018364bc3ee7c4bd7f25c28203737e1dd75668afd03857a64f02110000000b4ac5aa02000000000000000000

1 output(s) for total of 454.862969493000 dcy

stealth address amount amount idx
00: 1ea4e6dc766d33b14eb071dd9348af0bd6f2f78145cb7d828bc0e33f32a09015 454.862969493000 67586 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": 39283, "vin": [ { "gen": { "height": 39273 } } ], "vout": [ { "amount": 454862969493, "target": { "key": "1ea4e6dc766d33b14eb071dd9348af0bd6f2f78145cb7d828bc0e33f32a09015" } } ], "extra": [ 1, 202, 130, 195, 191, 230, 70, 35, 1, 131, 100, 188, 62, 231, 196, 189, 127, 37, 194, 130, 3, 115, 126, 29, 215, 86, 104, 175, 208, 56, 87, 166, 79, 2, 17, 0, 0, 0, 11, 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