Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70d74df1b2d34c66a902131975a9ed094eec9abd626dbfba29f65fdde39404ee

Tx prefix hash: 3ac9c2b6884bae6677c90a992cf81814cc2ccd559791d9e1b0f45a5b0b07426b
Tx public key: ec0d08e0bc248fc4b3b7b8b14834347533197338338c209dc787e177f5a054b9
Timestamp: 1675509041 Timestamp [UCT]: 2023-02-04 11:10:41 Age [y:d:h:m:s]: 02:027:09:33:26
Block: 689588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541178 RingCT/type: yes/0
Extra: 01ec0d08e0bc248fc4b3b7b8b14834347533197338338c209dc787e177f5a054b90211000000025029cbac000000000000000000

1 output(s) for total of 3.184994032000 dcy

stealth address amount amount idx
00: e6203e12127eb0e24c9390563dc3394d052eaa35f05ef398d372f4518ae52de8 3.184994032000 1132276 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": 689598, "vin": [ { "gen": { "height": 689588 } } ], "vout": [ { "amount": 3184994032, "target": { "key": "e6203e12127eb0e24c9390563dc3394d052eaa35f05ef398d372f4518ae52de8" } } ], "extra": [ 1, 236, 13, 8, 224, 188, 36, 143, 196, 179, 183, 184, 177, 72, 52, 52, 117, 51, 25, 115, 56, 51, 140, 32, 157, 199, 135, 225, 119, 245, 160, 84, 185, 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