Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0df34efb5d590aed6ad6b7d9d2f392c5f49783afd83623d2aafe8b66c8079dd0

Tx prefix hash: f69c75ffcb8fcefe110e451e3f64dc0641f49e923fd0236ea596df7d5af81715
Tx public key: 0f7f96efc018ef1a50e7e68dca0ee94c22f6c2392b55b610b0f9266b470f0c91
Timestamp: 1732130793 Timestamp [UCT]: 2024-11-20 19:26:33 Age [y:d:h:m:s]: 00:003:10:53:44
Block: 1158025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2469 RingCT/type: yes/0
Extra: 010f7f96efc018ef1a50e7e68dca0ee94c22f6c2392b55b610b0f9266b470f0c910211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf99dd0b4f9fdbc0f0cb5d97b1958cf7d1959fe2a18e96053f361cad1ebfd80 0.600000000000 1643652 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": 1158035, "vin": [ { "gen": { "height": 1158025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf99dd0b4f9fdbc0f0cb5d97b1958cf7d1959fe2a18e96053f361cad1ebfd80" } } ], "extra": [ 1, 15, 127, 150, 239, 192, 24, 239, 26, 80, 231, 230, 141, 202, 14, 233, 76, 34, 246, 194, 57, 43, 85, 182, 16, 176, 249, 38, 107, 71, 15, 12, 145, 2, 17, 0, 0, 0, 2, 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