Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cb6e31640ac7cd4ab4d396d684e6d52ff84c9ac70d951ae9c09d0549556550c

Tx prefix hash: 07818280b08c29ee288d39457ec4afdad5399ef098d3e9758669e0a217187e55
Tx public key: 9a5498e037c863537a3c8e86c25b8b6ff870b58c377c3ad98a1f59fda8615579
Timestamp: 1707371717 Timestamp [UCT]: 2024-02-08 05:55:17 Age [y:d:h:m:s]: 01:091:14:03:39
Block: 952859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326520 RingCT/type: yes/0
Extra: 019a5498e037c863537a3c8e86c25b8b6ff870b58c377c3ad98a1f59fda86155790211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e5669ea3d6e309f2fedc98eaa5a941e03c6c16fd6c66762c6bcf59a2406c833 0.600000000000 1411993 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": 952869, "vin": [ { "gen": { "height": 952859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e5669ea3d6e309f2fedc98eaa5a941e03c6c16fd6c66762c6bcf59a2406c833" } } ], "extra": [ 1, 154, 84, 152, 224, 55, 200, 99, 83, 122, 60, 142, 134, 194, 91, 139, 111, 248, 112, 181, 140, 55, 124, 58, 217, 138, 31, 89, 253, 168, 97, 85, 121, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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