Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb1f0ec386c8de7bbe826b5674fd0377cff5f827ba57fa130cacb2f7aa3f5980

Tx prefix hash: 49c47962466eae9e89b7ace5388be3f960caed854fa1d10b7f50dd2749928230
Tx public key: 570bc8298aafcf9fb1092d2b8b9c7d2fa7266aa2949b3d2fb3f8fbe50f8e9cdd
Timestamp: 1647793042 Timestamp [UCT]: 2022-03-20 16:17:22 Age [y:d:h:m:s]: 02:246:02:18:30
Block: 462642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695355 RingCT/type: yes/0
Extra: 01570bc8298aafcf9fb1092d2b8b9c7d2fa7266aa2949b3d2fb3f8fbe50f8e9cdd021100000002d3fcec30000000000000000000

1 output(s) for total of 17.991826831000 dcy

stealth address amount amount idx
00: 2757e746e293e113527ada13415a9a62bba1ca21d4532284ae72008bde349619 17.991826831000 880139 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": 462652, "vin": [ { "gen": { "height": 462642 } } ], "vout": [ { "amount": 17991826831, "target": { "key": "2757e746e293e113527ada13415a9a62bba1ca21d4532284ae72008bde349619" } } ], "extra": [ 1, 87, 11, 200, 41, 138, 175, 207, 159, 177, 9, 45, 43, 139, 156, 125, 47, 167, 38, 106, 162, 148, 155, 61, 47, 179, 248, 251, 229, 15, 142, 156, 221, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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