Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f84fe96354b25862a025f690f285249192f3ecd099a506e6cb0031944eb5dbec

Tx prefix hash: deb9388e4b5f8596804c6d5aae74ec80714b86f2e56f18217e4f46ac0e2cf7ef
Tx public key: 487b48db37363f21a646abf9843dab57da85c16b8cae092f2f6c607446d4f909
Timestamp: 1721140379 Timestamp [UCT]: 2024-07-16 14:32:59 Age [y:d:h:m:s]: 00:268:09:45:20
Block: 1067020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191746 RingCT/type: yes/0
Extra: 01487b48db37363f21a646abf9843dab57da85c16b8cae092f2f6c607446d4f909021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d0323c3c604e9215f7c57ef85c54c26d5f071ce9a4ca7c05f248dc8bc26fee3 0.600000000000 1537721 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": 1067030, "vin": [ { "gen": { "height": 1067020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d0323c3c604e9215f7c57ef85c54c26d5f071ce9a4ca7c05f248dc8bc26fee3" } } ], "extra": [ 1, 72, 123, 72, 219, 55, 54, 63, 33, 166, 70, 171, 249, 132, 61, 171, 87, 218, 133, 193, 107, 140, 174, 9, 47, 47, 108, 96, 116, 70, 212, 249, 9, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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