Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7f412101d564cdc3765dd373abe4475585818ebad594fde1f3fdbca1a5f180

Tx prefix hash: 0b228296c4d464422e3fe864aba8c5b8c74372b3c658d41c63c03c09e77b3a05
Tx public key: ad59f82a3671e7329dd4d3af9fd5c56863feaed403968ac0a1be1647719ff779
Timestamp: 1700085452 Timestamp [UCT]: 2023-11-15 21:57:32 Age [y:d:h:m:s]: 01:104:14:10:20
Block: 892455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335894 RingCT/type: yes/0
Extra: 01ad59f82a3671e7329dd4d3af9fd5c56863feaed403968ac0a1be1647719ff77902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.677526215000 dcy

stealth address amount amount idx
00: 32ca4f6589a7b66ae01e584f7ca5e035ea40c81899ef3d59c69f2025d9d28741 0.677526215000 1348574 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": 892465, "vin": [ { "gen": { "height": 892455 } } ], "vout": [ { "amount": 677526215, "target": { "key": "32ca4f6589a7b66ae01e584f7ca5e035ea40c81899ef3d59c69f2025d9d28741" } } ], "extra": [ 1, 173, 89, 248, 42, 54, 113, 231, 50, 157, 212, 211, 175, 159, 213, 197, 104, 99, 254, 174, 212, 3, 150, 138, 192, 161, 190, 22, 71, 113, 159, 247, 121, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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