Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14429ec1e44b5635c135a279f2ddd8d012a130d5f70e028e7d9552c5a6d09fd9

Tx prefix hash: 501a9475dea172ea9399f485bc27d1cc4dc21c32536f8fd9fee941eaa0fe84e6
Tx public key: b09f29548be3ac1cefd4a50e544993f6945510931558905c5f4cedd6f6e76b11
Timestamp: 1578669227 Timestamp [UCT]: 2020-01-10 15:13:47 Age [y:d:h:m:s]: 04:354:05:30:13
Block: 42796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142451 RingCT/type: yes/0
Extra: 01b09f29548be3ac1cefd4a50e544993f6945510931558905c5f4cedd6f6e76b110211000000144943cd9f000000000000000000

1 output(s) for total of 442.792167483000 dcy

stealth address amount amount idx
00: 4c2f985f2a22151816452249f4444f827103d2cfb943c9e2ed8d8131c224fbbc 442.792167483000 77205 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": 42806, "vin": [ { "gen": { "height": 42796 } } ], "vout": [ { "amount": 442792167483, "target": { "key": "4c2f985f2a22151816452249f4444f827103d2cfb943c9e2ed8d8131c224fbbc" } } ], "extra": [ 1, 176, 159, 41, 84, 139, 227, 172, 28, 239, 212, 165, 14, 84, 73, 147, 246, 148, 85, 16, 147, 21, 88, 144, 92, 95, 76, 237, 214, 246, 231, 107, 17, 2, 17, 0, 0, 0, 20, 73, 67, 205, 159, 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