Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353d80760b55b8d2757394e94d19b710f84abf64a506564f1255c4d867d7b8e8

Tx prefix hash: f74039df12658a4e16e37df8299303cd524b0e1531fa5d67c140ec45688d1696
Tx public key: e866dc7ec6e4012868fbea079a829bfd0f48933926dadd49f4a13a621d5d28b2
Timestamp: 1687320150 Timestamp [UCT]: 2023-06-21 04:02:30 Age [y:d:h:m:s]: 01:252:15:24:19
Block: 786872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441700 RingCT/type: yes/0
Extra: 01e866dc7ec6e4012868fbea079a829bfd0f48933926dadd49f4a13a621d5d28b202110000000233af99f4000000000000000000

1 output(s) for total of 1.516235173000 dcy

stealth address amount amount idx
00: b6867a27354d06d7d73bdf6364d74465fe99b8e4437c1757341727a7e89da394 1.516235173000 1236887 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": 786882, "vin": [ { "gen": { "height": 786872 } } ], "vout": [ { "amount": 1516235173, "target": { "key": "b6867a27354d06d7d73bdf6364d74465fe99b8e4437c1757341727a7e89da394" } } ], "extra": [ 1, 232, 102, 220, 126, 198, 228, 1, 40, 104, 251, 234, 7, 154, 130, 155, 253, 15, 72, 147, 57, 38, 218, 221, 73, 244, 161, 58, 98, 29, 93, 40, 178, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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