Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3fa2dc2093455768f6bba86a6df3734d42826197ea4acf92a91e84b9aa8e6a8

Tx prefix hash: 0e64e02ddbda08b253f8ff05326ae5ebfc82f4108b891ae625d97f168cdd3e70
Tx public key: 7d32310ce0caa98f07769565be5899eeea53e99a2c14d174d3d0aba200516167
Timestamp: 1705281589 Timestamp [UCT]: 2024-01-15 01:19:49 Age [y:d:h:m:s]: 01:304:03:21:37
Block: 935496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476215 RingCT/type: yes/0
Extra: 017d32310ce0caa98f07769565be5899eeea53e99a2c14d174d3d0aba20051616702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5504279a5ba8dd2d7b4111e241fefa9f24d932fea86f8d5ba04ddd03d659c352 0.600000000000 1393512 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": 935506, "vin": [ { "gen": { "height": 935496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5504279a5ba8dd2d7b4111e241fefa9f24d932fea86f8d5ba04ddd03d659c352" } } ], "extra": [ 1, 125, 50, 49, 12, 224, 202, 169, 143, 7, 118, 149, 101, 190, 88, 153, 238, 234, 83, 233, 154, 44, 20, 209, 116, 211, 208, 171, 162, 0, 81, 97, 103, 2, 17, 0, 0, 0, 5, 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