Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3776110d7108a43cc3558bedc4f6d48229b39c592818fa21d6ae8f21e8ce2cb8

Tx prefix hash: bcb07713ffa6ba2fa715b4c59a784c99210c65af5fb37055c4e28145c56befb4
Tx public key: b0cecdec1ed8e013be4e33a38363353e5ee7b6db1c691ea83babf298bdf49eaf
Timestamp: 1710041958 Timestamp [UCT]: 2024-03-10 03:39:18 Age [y:d:h:m:s]: 01:065:11:20:56
Block: 975004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307819 RingCT/type: yes/0
Extra: 01b0cecdec1ed8e013be4e33a38363353e5ee7b6db1c691ea83babf298bdf49eaf0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a4e5909bac52f32edb0ceaf55e421c9f800d3eb07a93ea86d41491a6405b692 0.600000000000 1434973 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": 975014, "vin": [ { "gen": { "height": 975004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a4e5909bac52f32edb0ceaf55e421c9f800d3eb07a93ea86d41491a6405b692" } } ], "extra": [ 1, 176, 206, 205, 236, 30, 216, 224, 19, 190, 78, 51, 163, 131, 99, 53, 62, 94, 231, 182, 219, 28, 105, 30, 168, 59, 171, 242, 152, 189, 244, 158, 175, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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