Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf77366232015f958ab4476844db568304525c2b7d6442af04c9f3919389509a

Tx prefix hash: 57ee05a3b0f5029c7d6622fd85d790294942e57e457c7a875a8ba6adee01f9e8
Tx public key: 190f6d7809b27fe1d251d08fa34a12d912e3ba422bf17c7014d5801b6effddbf
Timestamp: 1672864029 Timestamp [UCT]: 2023-01-04 20:27:09 Age [y:d:h:m:s]: 02:090:06:17:38
Block: 667647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 586174 RingCT/type: yes/0
Extra: 01190f6d7809b27fe1d251d08fa34a12d912e3ba422bf17c7014d5801b6effddbf02110000000183600029000000000000000000

1 output(s) for total of 3.765375533000 dcy

stealth address amount amount idx
00: bb9b58d713dffec1f0ee53a2a512fc870e2a7388e463ce6c1eb4f6b75b9a757a 3.765375533000 1108862 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": 667657, "vin": [ { "gen": { "height": 667647 } } ], "vout": [ { "amount": 3765375533, "target": { "key": "bb9b58d713dffec1f0ee53a2a512fc870e2a7388e463ce6c1eb4f6b75b9a757a" } } ], "extra": [ 1, 25, 15, 109, 120, 9, 178, 127, 225, 210, 81, 208, 143, 163, 74, 18, 217, 18, 227, 186, 66, 43, 241, 124, 112, 20, 213, 128, 27, 110, 255, 221, 191, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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