Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec377ae88739c8699421e1fdc1bf20be5801794092384c2373d55eb9c7cc6f41

Tx prefix hash: de47886e958e5c1ee748545df3c9fe95733044c0a46c7f0ebaecc896e80f5188
Tx public key: 68363f05967216c6bc7d7a51e2926cc49e234330298874f257ba64f39a3d7a0b
Timestamp: 1720603355 Timestamp [UCT]: 2024-07-10 09:22:35 Age [y:d:h:m:s]: 00:310:14:48:54
Block: 1062568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221945 RingCT/type: yes/0
Extra: 0168363f05967216c6bc7d7a51e2926cc49e234330298874f257ba64f39a3d7a0b02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f30669f7c9a4f872ab86ca2f070d8e3eca853c471a5e5b3d867ec04ae6f3231c 0.600000000000 1533073 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": 1062578, "vin": [ { "gen": { "height": 1062568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f30669f7c9a4f872ab86ca2f070d8e3eca853c471a5e5b3d867ec04ae6f3231c" } } ], "extra": [ 1, 104, 54, 63, 5, 150, 114, 22, 198, 188, 125, 122, 81, 226, 146, 108, 196, 158, 35, 67, 48, 41, 136, 116, 242, 87, 186, 100, 243, 154, 61, 122, 11, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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