Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23b3f2971f48325249b21675ddb1dc76e007e7baf9b8d6b26cc624bab34678c

Tx prefix hash: 68671e976af6db7052208a84e03fffd58626ec1ccaad447d2f938704bca76fd2
Tx public key: 531f663290ce2d88655e28b6106763ff1d4c18a6b648dd5db3b9f8f681e8e419
Timestamp: 1724850966 Timestamp [UCT]: 2024-08-28 13:16:06 Age [y:d:h:m:s]: 00:254:10:09:08
Block: 1097767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181721 RingCT/type: yes/0
Extra: 01531f663290ce2d88655e28b6106763ff1d4c18a6b648dd5db3b9f8f681e8e41902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cd98e8dbbd4966be82a836a8b78d1b8480343248f8425630e28e3613bbcc879 0.600000000000 1573250 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": 1097777, "vin": [ { "gen": { "height": 1097767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cd98e8dbbd4966be82a836a8b78d1b8480343248f8425630e28e3613bbcc879" } } ], "extra": [ 1, 83, 31, 102, 50, 144, 206, 45, 136, 101, 94, 40, 182, 16, 103, 99, 255, 29, 76, 24, 166, 182, 72, 221, 93, 179, 185, 248, 246, 129, 232, 228, 25, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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