Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bf4ff4f1c41a1bb5f1ed3986450a5140bede146d99035e27c06e433b30d8a98

Tx prefix hash: 732b2694f411195e71480903c4e6a1724797e02500d637254858eec201470eb7
Tx public key: 369b0add0e35622e17f8965b354cd414c68ae77b9725683d2912c5240adbb7a0
Timestamp: 1710548183 Timestamp [UCT]: 2024-03-16 00:16:23 Age [y:d:h:m:s]: 01:044:02:44:10
Block: 979214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292519 RingCT/type: yes/0
Extra: 01369b0add0e35622e17f8965b354cd414c68ae77b9725683d2912c5240adbb7a00211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4f30fb77fb6b132ecf20a746338bcf362cb2e6f2ab75b52c84ed0ae4e7d2d31 0.600000000000 1439247 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": 979224, "vin": [ { "gen": { "height": 979214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4f30fb77fb6b132ecf20a746338bcf362cb2e6f2ab75b52c84ed0ae4e7d2d31" } } ], "extra": [ 1, 54, 155, 10, 221, 14, 53, 98, 46, 23, 248, 150, 91, 53, 76, 212, 20, 198, 138, 231, 123, 151, 37, 104, 61, 41, 18, 197, 36, 10, 219, 183, 160, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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