Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdcf419df45e3bc0af8bded7c03644289705dce44c24b196fe7b68e3e4b41dfe

Tx prefix hash: e2e05440e7089241871eb20cb9ba3e85dbcc39e26f008a4f7a419b3cfb27b115
Tx public key: 9976ed026ca1957d03afbb6c52f1b54fab15739953993b793fa70d0941f9d5fe
Timestamp: 1657048507 Timestamp [UCT]: 2022-07-05 19:15:07 Age [y:d:h:m:s]: 02:231:03:04:21
Block: 537370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 686273 RingCT/type: yes/0
Extra: 019976ed026ca1957d03afbb6c52f1b54fab15739953993b793fa70d0941f9d5fe021100000001a8c141c5000000000000000000

1 output(s) for total of 10.177627153000 dcy

stealth address amount amount idx
00: 1b602e93e80f22197c0334c7994848e2662933668d8b791f66c0bf404e1f5341 10.177627153000 967247 of 0

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": 537380, "vin": [ { "gen": { "height": 537370 } } ], "vout": [ { "amount": 10177627153, "target": { "key": "1b602e93e80f22197c0334c7994848e2662933668d8b791f66c0bf404e1f5341" } } ], "extra": [ 1, 153, 118, 237, 2, 108, 161, 149, 125, 3, 175, 187, 108, 82, 241, 181, 79, 171, 21, 115, 153, 83, 153, 59, 121, 63, 167, 13, 9, 65, 249, 213, 254, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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