Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c95f9c641d78b9f7b96bba8b68acab6a776c824df9f9378f4e5cd3aaa6939e1

Tx prefix hash: f76ccf3118eae15eea4aa54d400f840e3227165090c9487e57feb5b247b1bdc9
Tx public key: 0e59bf80fcbfd5bde0d243c614ae061ddf5226f16140328e531d85601ed73c81
Timestamp: 1733173506 Timestamp [UCT]: 2024-12-02 21:05:06 Age [y:d:h:m:s]: 00:109:07:36:24
Block: 1166678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77917 RingCT/type: yes/0
Extra: 010e59bf80fcbfd5bde0d243c614ae061ddf5226f16140328e531d85601ed73c810211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b01531382badcfde975420d0cdc502173e89b645cd7a5215b4d5bce458f59654 0.600000000000 1652367 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": 1166688, "vin": [ { "gen": { "height": 1166678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b01531382badcfde975420d0cdc502173e89b645cd7a5215b4d5bce458f59654" } } ], "extra": [ 1, 14, 89, 191, 128, 252, 191, 213, 189, 224, 210, 67, 198, 20, 174, 6, 29, 223, 82, 38, 241, 97, 64, 50, 142, 83, 29, 133, 96, 30, 215, 60, 129, 2, 17, 0, 0, 0, 3, 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