Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b760c9a856966b812ce4af6a565b4cf3ee44616cc1ade8fc01c468f4b6cedeac

Tx prefix hash: 580a6cc9a44e47ea2195c4637446ea31ad810699f44d86152a9cdea9be9bfae1
Tx public key: 89a451a582146e1bb8b0aaec7b4d1f3bb5b06767957fec43cc3978bf2ae8ddce
Timestamp: 1721007174 Timestamp [UCT]: 2024-07-15 01:32:54 Age [y:d:h:m:s]: 00:269:02:01:40
Block: 1065919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192233 RingCT/type: yes/0
Extra: 0189a451a582146e1bb8b0aaec7b4d1f3bb5b06767957fec43cc3978bf2ae8ddce02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5d701eed17c5965ae25d2ed5232272b43fa93c9abd423e0f92dd90babf3134 0.600000000000 1536488 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": 1065929, "vin": [ { "gen": { "height": 1065919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5d701eed17c5965ae25d2ed5232272b43fa93c9abd423e0f92dd90babf3134" } } ], "extra": [ 1, 137, 164, 81, 165, 130, 20, 110, 27, 184, 176, 170, 236, 123, 77, 31, 59, 181, 176, 103, 103, 149, 127, 236, 67, 204, 57, 120, 191, 42, 232, 221, 206, 2, 17, 0, 0, 0, 3, 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