Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 948c1b5a4c91b5e698c967f1d42bc8358efa3e20d9fb4d19d6c6cd0dfb282c42

Tx prefix hash: 01f03caf575aedf60ec97590d5af76b0387b386f0e80fa04480d7a880228d483
Tx public key: ea7767c672e4c4a2747d59b52a205b77bb8eaf455131df90f180d580181b7249
Timestamp: 1711480956 Timestamp [UCT]: 2024-03-26 19:22:36 Age [y:d:h:m:s]: 01:031:15:07:16
Block: 986955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283565 RingCT/type: yes/0
Extra: 01ea7767c672e4c4a2747d59b52a205b77bb8eaf455131df90f180d580181b724902110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb631d698b55e28e7391c4d027027056a2aad9197e0945479a052d84df96eb51 0.600000000000 1447192 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": 986965, "vin": [ { "gen": { "height": 986955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb631d698b55e28e7391c4d027027056a2aad9197e0945479a052d84df96eb51" } } ], "extra": [ 1, 234, 119, 103, 198, 114, 228, 196, 162, 116, 125, 89, 181, 42, 32, 91, 119, 187, 142, 175, 69, 81, 49, 223, 144, 241, 128, 213, 128, 24, 27, 114, 73, 2, 17, 0, 0, 0, 11, 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