Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44de9b668ae747665608e0ed254374ac28108ceceb2e883ab791437aa99f7f8c

Tx prefix hash: dd2cf511fbe3933ac14929867f5d169c98f5d9abde1c936f9e793d28ea64d87d
Tx public key: 7db6b1d98f3fbb744043d58b3e7b954e054f828d79263a4335edfffa08b3e5ae
Timestamp: 1680982535 Timestamp [UCT]: 2023-04-08 19:35:35 Age [y:d:h:m:s]: 01:361:16:58:14
Block: 734381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519746 RingCT/type: yes/0
Extra: 017db6b1d98f3fbb744043d58b3e7b954e054f828d79263a4335edfffa08b3e5ae021100000001faf35c9c000000000000000000

1 output(s) for total of 2.263034198000 dcy

stealth address amount amount idx
00: 3e91dfa3334311aa26c5197c6dee69ab8b2bb991dff2c7aa0e011d630a1d8478 2.263034198000 1180576 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": 734391, "vin": [ { "gen": { "height": 734381 } } ], "vout": [ { "amount": 2263034198, "target": { "key": "3e91dfa3334311aa26c5197c6dee69ab8b2bb991dff2c7aa0e011d630a1d8478" } } ], "extra": [ 1, 125, 182, 177, 217, 143, 63, 187, 116, 64, 67, 213, 139, 62, 123, 149, 78, 5, 79, 130, 141, 121, 38, 58, 67, 53, 237, 255, 250, 8, 179, 229, 174, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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