Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0affa341c9522ae5586f04c5b001266bb0a27ea6dba5d66aec2b5dea06a13c77

Tx prefix hash: 1eb56350b0abfb8c2d7f6bd62051397850727d45e3c241efddb895af2e5dd4fa
Tx public key: 838f443975641fa99109d8d8dcf27b764970cd5ed061c761a84de5d439a39cc6
Timestamp: 1735158837 Timestamp [UCT]: 2024-12-25 20:33:57 Age [y:d:h:m:s]: 00:095:04:01:10
Block: 1183112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67793 RingCT/type: yes/0
Extra: 01838f443975641fa99109d8d8dcf27b764970cd5ed061c761a84de5d439a39cc6021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33f2e4f034ff5ec1ebebf155e9e66e9c84f519d4c8c3383ee2e70c915f7804cf 0.600000000000 1669553 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": 1183122, "vin": [ { "gen": { "height": 1183112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33f2e4f034ff5ec1ebebf155e9e66e9c84f519d4c8c3383ee2e70c915f7804cf" } } ], "extra": [ 1, 131, 143, 68, 57, 117, 100, 31, 169, 145, 9, 216, 216, 220, 242, 123, 118, 73, 112, 205, 94, 208, 97, 199, 97, 168, 77, 229, 212, 57, 163, 156, 198, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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