Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 227b7cc4fb4f7702cb968e3a3773823765b7a1d4dc97b0dea27bc43cf3998ddf

Tx prefix hash: 66ef28121c729d1b68235d96faae2139dd5df0f80d70379b8079803fa9b43137
Tx public key: 5b74fae9e95c68e760271377a5cdd8f40c5a5dc74122625c046123c072e9987e
Timestamp: 1581804879 Timestamp [UCT]: 2020-02-15 22:14:39 Age [y:d:h:m:s]: 04:288:10:59:22
Block: 65586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098584 RingCT/type: yes/0
Extra: 015b74fae9e95c68e760271377a5cdd8f40c5a5dc74122625c046123c072e9987e021100000004d81c26c0000000000000000000

1 output(s) for total of 372.123559166000 dcy

stealth address amount amount idx
00: de8ab676716f56eb832667888a52385e80fad102b5675b46ad204829370afbf5 372.123559166000 121045 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": 65596, "vin": [ { "gen": { "height": 65586 } } ], "vout": [ { "amount": 372123559166, "target": { "key": "de8ab676716f56eb832667888a52385e80fad102b5675b46ad204829370afbf5" } } ], "extra": [ 1, 91, 116, 250, 233, 233, 92, 104, 231, 96, 39, 19, 119, 165, 205, 216, 244, 12, 90, 93, 199, 65, 34, 98, 92, 4, 97, 35, 192, 114, 233, 152, 126, 2, 17, 0, 0, 0, 4, 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