Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdf1ef2b45afaf569505951f109134656d902597cf32709b852e02be9e10985a

Tx prefix hash: f049e32f482c7683e747dc1c9ab180895968b71eeb10498bbd4f06343bcd061d
Tx public key: 1dfb08cea2e5c85275c3df86ed5b9d7d1a4b7648ddaff5f1243aeca54be52c7a
Timestamp: 1662075127 Timestamp [UCT]: 2022-09-01 23:32:07 Age [y:d:h:m:s]: 02:211:03:13:06
Block: 578828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 672139 RingCT/type: yes/0
Extra: 011dfb08cea2e5c85275c3df86ed5b9d7d1a4b7648ddaff5f1243aeca54be52c7a021100000013e6d27f9c000000000000000000

1 output(s) for total of 7.414854666000 dcy

stealth address amount amount idx
00: 9a8f8b0de9fae32aeedb4c4f08f2f585bad43dff1e089f504c2b37a2eddac5c2 7.414854666000 1012252 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": 578838, "vin": [ { "gen": { "height": 578828 } } ], "vout": [ { "amount": 7414854666, "target": { "key": "9a8f8b0de9fae32aeedb4c4f08f2f585bad43dff1e089f504c2b37a2eddac5c2" } } ], "extra": [ 1, 29, 251, 8, 206, 162, 229, 200, 82, 117, 195, 223, 134, 237, 91, 157, 125, 26, 75, 118, 72, 221, 175, 245, 241, 36, 58, 236, 165, 75, 229, 44, 122, 2, 17, 0, 0, 0, 19, 230, 210, 127, 156, 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