Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee6052b4c0e69770e3a9e49a208b74e948d2041aa141438be9fadbea5046b90f

Tx prefix hash: 4df1ea6ac05e20fc526a838e36fd67a35d84d6eb1c7631a06a5784c5d825feb0
Tx public key: 58a95592f0ed8b427bfde613e504fff70f4bbf9921b1a935e7dfb20c6e2ca94a
Timestamp: 1735035714 Timestamp [UCT]: 2024-12-24 10:21:54 Age [y:d:h:m:s]: 00:099:06:41:04
Block: 1182099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70730 RingCT/type: yes/0
Extra: 0158a95592f0ed8b427bfde613e504fff70f4bbf9921b1a935e7dfb20c6e2ca94a0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93834516e58e5c55ec4e8ef25fafc71733b56f207377120ac1abc8376e16e801 0.600000000000 1668530 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": 1182109, "vin": [ { "gen": { "height": 1182099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93834516e58e5c55ec4e8ef25fafc71733b56f207377120ac1abc8376e16e801" } } ], "extra": [ 1, 88, 169, 85, 146, 240, 237, 139, 66, 123, 253, 230, 19, 229, 4, 255, 247, 15, 75, 191, 153, 33, 177, 169, 53, 231, 223, 178, 12, 110, 44, 169, 74, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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