Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 045de36824be4e42190346b5f3f0738b4eeb316adc1f5eb2c0af1ae3c95963a1

Tx prefix hash: a4e7cee4ab47ab577d48ab3f90e91562cb4786874dca22b847ef4a2866ec3a0f
Tx public key: b70ac620f859ad62ce6c0e3291010cd7b5f665f632c6b7e306b1c6569377fb95
Timestamp: 1714314217 Timestamp [UCT]: 2024-04-28 14:23:37 Age [y:d:h:m:s]: 01:038:02:06:42
Block: 1010411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288208 RingCT/type: yes/0
Extra: 01b70ac620f859ad62ce6c0e3291010cd7b5f665f632c6b7e306b1c6569377fb9502110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6aa2eb1754c9b288df94853e8df8f2a57a5a6830c9fb6cd2aec28154e1f68a 0.600000000000 1472359 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": 1010421, "vin": [ { "gen": { "height": 1010411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6aa2eb1754c9b288df94853e8df8f2a57a5a6830c9fb6cd2aec28154e1f68a" } } ], "extra": [ 1, 183, 10, 198, 32, 248, 89, 173, 98, 206, 108, 14, 50, 145, 1, 12, 215, 181, 246, 101, 246, 50, 198, 183, 227, 6, 177, 198, 86, 147, 119, 251, 149, 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