Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364ec04faea0c1ce47c864f3835c2d8f879a0ec845c3797758554fef8511e4db

Tx prefix hash: 2aa95ac8daf96d0a16c6c238661ee5ef064f283316b636e7a11b344a310de59b
Tx public key: 1f4ceeef0bb6de462057121c9d7573680bc518dc3138051c239faf3f23b99857
Timestamp: 1639498479 Timestamp [UCT]: 2021-12-14 16:14:39 Age [y:d:h:m:s]: 03:023:16:21:12
Block: 395444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795902 RingCT/type: yes/0
Extra: 011f4ceeef0bb6de462057121c9d7573680bc518dc3138051c239faf3f23b998570211000000054a0f5013000000000000000000

1 output(s) for total of 30.042095994000 dcy

stealth address amount amount idx
00: 40ebcfe0b651dbbc5986c3f063c0fbc6784b6f7decbd80bfe6528f0b34550262 30.042095994000 793365 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": 395454, "vin": [ { "gen": { "height": 395444 } } ], "vout": [ { "amount": 30042095994, "target": { "key": "40ebcfe0b651dbbc5986c3f063c0fbc6784b6f7decbd80bfe6528f0b34550262" } } ], "extra": [ 1, 31, 76, 238, 239, 11, 182, 222, 70, 32, 87, 18, 28, 157, 117, 115, 104, 11, 197, 24, 220, 49, 56, 5, 28, 35, 159, 175, 63, 35, 185, 152, 87, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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