Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebec4c8d4368131f183ae3a6673ece2b168191eab8ba85bea25ac792ea7d8845

Tx prefix hash: 2f24cd24da4390d1fdebe1f1a81b1e22f009a76143498f3b031e56b21928c017
Tx public key: d4d96d31e6d6d9298ccd7a653aefdc75b49d25dd7540d22e4cf28f41b80c779b
Timestamp: 1736680298 Timestamp [UCT]: 2025-01-12 11:11:38 Age [y:d:h:m:s]: 00:095:23:02:41
Block: 1195699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68375 RingCT/type: yes/0
Extra: 01d4d96d31e6d6d9298ccd7a653aefdc75b49d25dd7540d22e4cf28f41b80c779b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c11c8c9763be9125aaf98d7594c275ab9066440ab55eecb321cc91b7580038a1 0.600000000000 1682290 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": 1195709, "vin": [ { "gen": { "height": 1195699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c11c8c9763be9125aaf98d7594c275ab9066440ab55eecb321cc91b7580038a1" } } ], "extra": [ 1, 212, 217, 109, 49, 230, 214, 217, 41, 140, 205, 122, 101, 58, 239, 220, 117, 180, 157, 37, 221, 117, 64, 210, 46, 76, 242, 143, 65, 184, 12, 119, 155, 2, 17, 0, 0, 0, 1, 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