Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7beef3d72cea3a12c4f84b23eafe5a9c8b1aa54fc05eeda5ab8132493daf8035

Tx prefix hash: 19e9e2ab0a88c95797e978f10d85ba2e9cd36b4df45915278695f9fcdf41119e
Tx public key: d75820d46c798d844da3fd13339e750810b6ed2a4a541d8bed6addb5a965736d
Timestamp: 1733693638 Timestamp [UCT]: 2024-12-08 21:33:58 Age [y:d:h:m:s]: 00:107:06:12:41
Block: 1170998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76417 RingCT/type: yes/0
Extra: 01d75820d46c798d844da3fd13339e750810b6ed2a4a541d8bed6addb5a965736d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3306fc97c1ed50f7fe4625b7dfde073fa33205eab71c876f625385399b5e352 0.600000000000 1656733 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": 1171008, "vin": [ { "gen": { "height": 1170998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3306fc97c1ed50f7fe4625b7dfde073fa33205eab71c876f625385399b5e352" } } ], "extra": [ 1, 215, 88, 32, 212, 108, 121, 141, 132, 77, 163, 253, 19, 51, 158, 117, 8, 16, 182, 237, 42, 74, 84, 29, 139, 237, 106, 221, 181, 169, 101, 115, 109, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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