Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddcbe530203480ea7c274e1a0a915f6798176ee90a0c6321af53b5ba3ab664df

Tx prefix hash: 3fd7f3e4a2d33e8f60590f9d79a7eaa63b45eaea51228a7580661c7a5ca5c66c
Tx public key: 1fde2982817e0c3dfb5da359bf653bc95e9de230fd1111e471544ae6463d67f9
Timestamp: 1681347450 Timestamp [UCT]: 2023-04-13 00:57:30 Age [y:d:h:m:s]: 02:202:18:16:42
Block: 737341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664789 RingCT/type: yes/0
Extra: 011fde2982817e0c3dfb5da359bf653bc95e9de230fd1111e471544ae6463d67f90211000000025029cbac000000000000000000

1 output(s) for total of 2.212500634000 dcy

stealth address amount amount idx
00: 6aa59431126534c056b13db98392f04972149ea7995f18fdfd0510732e989f20 2.212500634000 1183886 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": 737351, "vin": [ { "gen": { "height": 737341 } } ], "vout": [ { "amount": 2212500634, "target": { "key": "6aa59431126534c056b13db98392f04972149ea7995f18fdfd0510732e989f20" } } ], "extra": [ 1, 31, 222, 41, 130, 129, 126, 12, 61, 251, 93, 163, 89, 191, 101, 59, 201, 94, 157, 226, 48, 253, 17, 17, 228, 113, 84, 74, 230, 70, 61, 103, 249, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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