Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40a65e9dd02cbc09cca2054a51ebb80d61dadaba65c6190e44d82e252f7b7643

Tx prefix hash: 9262a89e1e0483e47fb6fe60647d852ec2518955e59c22c394afe6ffe446ccdd
Tx public key: e1f6d942f5038762e2d94b814e9c693e081beaa52947d239e9c08c6dc86c1f19
Timestamp: 1716192371 Timestamp [UCT]: 2024-05-20 08:06:11 Age [y:d:h:m:s]: 00:282:06:04:33
Block: 1025987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201716 RingCT/type: yes/0
Extra: 01e1f6d942f5038762e2d94b814e9c693e081beaa52947d239e9c08c6dc86c1f1902110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51901af5a1ef889ff907b23dbf53a4f303273a7474f3380924a23f1054158817 0.600000000000 1492824 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": 1025997, "vin": [ { "gen": { "height": 1025987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51901af5a1ef889ff907b23dbf53a4f303273a7474f3380924a23f1054158817" } } ], "extra": [ 1, 225, 246, 217, 66, 245, 3, 135, 98, 226, 217, 75, 129, 78, 156, 105, 62, 8, 27, 234, 165, 41, 71, 210, 57, 233, 192, 140, 109, 200, 108, 31, 25, 2, 17, 0, 0, 0, 8, 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