Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef5c8bec11c7f4be81bd91d31f6cf5db0b3bed350fee7936498d0f906e989c2d

Tx prefix hash: b8d8d14b69bf0bfc77b9fcdb94f0b66ce6310ee812d0eeb5778aadfaf962de6e
Tx public key: bc9fa9775a441c1143bdfe5b67aa98a09d095ba5ccd6ff8d691e4b1e30366ff3
Timestamp: 1578411168 Timestamp [UCT]: 2020-01-07 15:32:48 Age [y:d:h:m:s]: 05:048:07:27:54
Block: 40618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184476 RingCT/type: yes/0
Extra: 01bc9fa9775a441c1143bdfe5b67aa98a09d095ba5ccd6ff8d691e4b1e30366ff3021100000014d81c26c0000000000000000000

1 output(s) for total of 450.221225962000 dcy

stealth address amount amount idx
00: 73937ecc24d3a1617578ca36c9e56f3edeaa12d2ad92c2f818eebe9ed4e6bb40 450.221225962000 71479 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": 40628, "vin": [ { "gen": { "height": 40618 } } ], "vout": [ { "amount": 450221225962, "target": { "key": "73937ecc24d3a1617578ca36c9e56f3edeaa12d2ad92c2f818eebe9ed4e6bb40" } } ], "extra": [ 1, 188, 159, 169, 119, 90, 68, 28, 17, 67, 189, 254, 91, 103, 170, 152, 160, 157, 9, 91, 165, 204, 214, 255, 141, 105, 30, 75, 30, 48, 54, 111, 243, 2, 17, 0, 0, 0, 20, 216, 28, 38, 192, 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