Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f80c5acf320aabb93d1744c06f1588ea98f6a09cb3a12768e46ee4dbb2fa9ac6

Tx prefix hash: dd5db5ee76bca8b544552446f3ac7f5bfd34d8540b45b87ac0d4877268116be0
Tx public key: a922970c129ce224b05228b572156a4dab8a1f662be8a5f4726dc37f59fabacf
Timestamp: 1627718546 Timestamp [UCT]: 2021-07-31 08:02:26 Age [y:d:h:m:s]: 03:302:13:18:02
Block: 304394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 988630 RingCT/type: yes/0
Extra: 01a922970c129ce224b05228b572156a4dab8a1f662be8a5f4726dc37f59fabacf0211000000b617696b73000000000000000000

1 output(s) for total of 60.175097427000 dcy

stealth address amount amount idx
00: 83ef474c0170a40ce7f5ccc711a4f0a22ba9cc65f2ad0f419dced33b4e87c40e 60.175097427000 635115 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": 304404, "vin": [ { "gen": { "height": 304394 } } ], "vout": [ { "amount": 60175097427, "target": { "key": "83ef474c0170a40ce7f5ccc711a4f0a22ba9cc65f2ad0f419dced33b4e87c40e" } } ], "extra": [ 1, 169, 34, 151, 12, 18, 156, 226, 36, 176, 82, 40, 181, 114, 21, 106, 77, 171, 138, 31, 102, 43, 232, 165, 244, 114, 109, 195, 127, 89, 250, 186, 207, 2, 17, 0, 0, 0, 182, 23, 105, 107, 115, 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