Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 485ac07890d8a7083211343cecff6f6268f169ebed46541e815a661664e7ba30

Tx prefix hash: 383d21703e06c6a16a841aba1cfa3787bf418f209e55e040d5aa0036c0cd5769
Tx public key: fed1a3f59658b8232cd999e60f3b04295054c36d3758ed14e03c4c542e0f81b5
Timestamp: 1623054590 Timestamp [UCT]: 2021-06-07 08:29:50 Age [y:d:h:m:s]: 03:200:04:21:24
Block: 273769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 907706 RingCT/type: yes/0
Extra: 01fed1a3f59658b8232cd999e60f3b04295054c36d3758ed14e03c4c542e0f81b502110000000323fdb90b000000000000000000

1 output(s) for total of 76.013404566000 dcy

stealth address amount amount idx
00: 1a7b6236c813be892883ef3727f3332cda8e75345ab323e517e188db7fb44e9b 76.013404566000 574372 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": 273779, "vin": [ { "gen": { "height": 273769 } } ], "vout": [ { "amount": 76013404566, "target": { "key": "1a7b6236c813be892883ef3727f3332cda8e75345ab323e517e188db7fb44e9b" } } ], "extra": [ 1, 254, 209, 163, 245, 150, 88, 184, 35, 44, 217, 153, 230, 15, 59, 4, 41, 80, 84, 195, 109, 55, 88, 237, 20, 224, 60, 76, 84, 46, 15, 129, 181, 2, 17, 0, 0, 0, 3, 35, 253, 185, 11, 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