Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f4021f683c7e2d7a52b6edf292a3eecb7c849a4bd6d5dc8a85c80ef32dd70d2

Tx prefix hash: a63398b217596f4b5aaa9de589058c92a6967eb384966234b60900c89e2cba90
Tx public key: d71aa9714abf34ca24d49275e9b54f4091eea456e140a8e777948679fb5dd651
Timestamp: 1681031699 Timestamp [UCT]: 2023-04-09 09:14:59 Age [y:d:h:m:s]: 01:362:20:30:59
Block: 734739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520615 RingCT/type: yes/0
Extra: 01d71aa9714abf34ca24d49275e9b54f4091eea456e140a8e777948679fb5dd651021100000003b3164c24000000000000000000

1 output(s) for total of 2.256861531000 dcy

stealth address amount amount idx
00: c6af4ad9141c149a6202ce43e39d23c4f1e7688061eeb8d63c47cb4f6cfedae2 2.256861531000 1180988 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": 734749, "vin": [ { "gen": { "height": 734739 } } ], "vout": [ { "amount": 2256861531, "target": { "key": "c6af4ad9141c149a6202ce43e39d23c4f1e7688061eeb8d63c47cb4f6cfedae2" } } ], "extra": [ 1, 215, 26, 169, 113, 74, 191, 52, 202, 36, 212, 146, 117, 233, 181, 79, 64, 145, 238, 164, 86, 225, 64, 168, 231, 119, 148, 134, 121, 251, 93, 214, 81, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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