Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e487651e25b292554551fc27315e6331f4c6f4f2a0439bbd80fe876fe7e513eb

Tx prefix hash: bb443f869790f160f3e644e99e33ef2fe3fc0df2e779d6bda848e129d37f2a19
Tx public key: 977c0e88f914cc33e908a7737740a629511f5dec493f3ae03ba558ba7eed2ec6
Timestamp: 1710790657 Timestamp [UCT]: 2024-03-18 19:37:37 Age [y:d:h:m:s]: 01:279:13:18:30
Block: 981228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458531 RingCT/type: yes/0
Extra: 01977c0e88f914cc33e908a7737740a629511f5dec493f3ae03ba558ba7eed2ec602110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d053147a7fcc27ad7e9be7b95407986bc9e127f854916b4f670a0a536c8d68c 0.600000000000 1441321 of 15

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": 981238, "vin": [ { "gen": { "height": 981228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d053147a7fcc27ad7e9be7b95407986bc9e127f854916b4f670a0a536c8d68c" } } ], "extra": [ 1, 151, 124, 14, 136, 249, 20, 204, 51, 233, 8, 167, 115, 119, 64, 166, 41, 81, 31, 93, 236, 73, 63, 58, 224, 59, 165, 88, 186, 126, 237, 46, 198, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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