Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f62d3aa68bdfb9e4f31efca0309044cc61ec15ad07926cad1b63a5f35bfe4e0a

Tx prefix hash: 673fc7cadd37266cdf10c14fc6cb2cd6b1d20f086ac8ac6f5ce4405c63f688b0
Tx public key: 2349e02462142f0db96eb77261312521c666a522f92c393c0df554e152abd6f0
Timestamp: 1669847989 Timestamp [UCT]: 2022-11-30 22:39:49 Age [y:d:h:m:s]: 02:047:00:00:18
Block: 642677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 555505 RingCT/type: yes/0
Extra: 012349e02462142f0db96eb77261312521c666a522f92c393c0df554e152abd6f0021100000002faf35c9c000000000000000000

1 output(s) for total of 4.555586616000 dcy

stealth address amount amount idx
00: 31ec979a7340116b9bfdc3dfe7cff253c64b00c14d1b4c60f7f7f6e02e7e46de 4.555586616000 1082578 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": 642687, "vin": [ { "gen": { "height": 642677 } } ], "vout": [ { "amount": 4555586616, "target": { "key": "31ec979a7340116b9bfdc3dfe7cff253c64b00c14d1b4c60f7f7f6e02e7e46de" } } ], "extra": [ 1, 35, 73, 224, 36, 98, 20, 47, 13, 185, 110, 183, 114, 97, 49, 37, 33, 198, 102, 165, 34, 249, 44, 57, 60, 13, 245, 84, 225, 82, 171, 214, 240, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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