Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e23e8fc18eda51824d5e665b8646aa20c0675e22d6ce63009c1ebba4b9dbffb

Tx prefix hash: 48e3cc3ad0f2d6a5145b1e5710b446c43748edb45e23a3d89039e1020fa22913
Tx public key: af2d41eeac5ead13c79859cdd6201c0c3375b66911f4b3eddc50e0cea1aa4cda
Timestamp: 1733978733 Timestamp [UCT]: 2024-12-12 04:45:33 Age [y:d:h:m:s]: 00:024:01:42:28
Block: 1173354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17212 RingCT/type: yes/0
Extra: 01af2d41eeac5ead13c79859cdd6201c0c3375b66911f4b3eddc50e0cea1aa4cda021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ed380f44474542937fcd79f3af08cc4b1eb344c27d8a228df5710bac0d20c1 0.600000000000 1659367 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": 1173364, "vin": [ { "gen": { "height": 1173354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ed380f44474542937fcd79f3af08cc4b1eb344c27d8a228df5710bac0d20c1" } } ], "extra": [ 1, 175, 45, 65, 238, 172, 94, 173, 19, 199, 152, 89, 205, 214, 32, 28, 12, 51, 117, 182, 105, 17, 244, 179, 237, 220, 80, 224, 206, 161, 170, 76, 218, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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